Repository navigation
Point to artifact verification from the security policy - #8
Merged
Merged
Conversation
Add a "Verifying our artifacts" section. It says that the artifacts we publish to Maven repositories carry SLSA build provenance, what checking it proves and what it doesn't, and that older versions may carry none. The command and the details live on spine.io, at Documentation > Security > Verifying artifacts, which the section links to. Also point the CVD Policy link to its new address, https://spine.io/docs/security/cvd-policy/. The old one redirects there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
armiol
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 2 of the Security section rollout. The site side is live: SpineEventEngine/documentation#88 and SpineEventEngine/SpineEventEngine.github.io#554.
What changed in
SECURITY.mdNew section, "Verifying our artifacts", after "Third-party components". It's a pointer with no commands:
The full instructions live at https://spine.io/docs/security/verifying-artifacts/. This follows the pattern of Argo CD, Kubernetes and Kyverno: the site holds the procedure, and
SECURITY.mdpoints to it.CVD Policy link now points to its canonical URL, https://spine.io/docs/security/cvd-policy/. The old
/cvd-policy/keeps redirecting there for links elsewhere.Why it's worded this way
SECURITY.mdfor every repository of the organization."From a protected branch" holds for the repositories checked:
masterof.githubandbase-librarieshas a ruleset that blocks deletion and force-pushes and requires pull requests.Checks
After merging
Run the spine.io Deploy to GitHub Pages workflow by hand (Run workflow on
master), so https://spine.io/docs/security/policy/ picks up this version without waiting for the next commit there.🤖 Generated with Claude Code